Thank you for your contribution! Unfortunately, the contracts are quite dynamic and can't be that easily annotated.

• Validators can be not Callable
• Contracts may also return strings instead of bool (and I think any other falsy/truely value).

For type checking in mypy, use the mypy plugin that comes with deal. I'd be happy to provide a plugin for pylance and pyright but pyright doesn't support plugins and not going to.

I'm still not sure what to do with the external validators support. I'm considering removing it altogether and just sticking to Callable contracts but external validators might be very handy for advanced payload validation in services. Maybe it doesn't matter much now that we have pydantic widely used, though, especially in FastAPI services.

@orsinium understood, thank you for the continued education here!

I didn't grok the external schema support when I read the docs first — that's actually neat feature for advanced payload validation, like you're saying.

Say I had something like:

`class UnvalidatedFileMetadata(SQLModel):
user_id: UUID = Field(default=None, foreign_key="user.id")
file_name: ValidString = Field(default=None)
file_path: ValidString = Field(default=None)

class FileMetadata(UnvalidatedFileMetadata, table=True):
tablename = "file_metadata" # type: ignore
id: UUID = Field(default_factory=uuid4, primary_key=True)
created_at: datetime = Field(default=datetime.utcnow(), nullable=False)
updated_at: datetime = Field(default_factory=datetime.utcnow, nullable=False)`

Using sqlmodel from the fastapi ecosystem. I could imagine using deal to validate that the input is specifically UnvalidatedFileMetadata at runtime to catch if devs try to pass FileMetadata to a function, thus accidentally skipping validation. May be a bit niche, but that's where my head goes.

Closing this PR, thanks again.

Thank you for your work! I'll see if the type annotations still can be improved a bit. I'll ping you for review when and if I have something :)